Internet Info 1994 March

home *** CD-ROM | disk | FTP | other *** search

/ Internet Info 1994 March / Internet Info CD-ROM (Walnut Creek) (March 1994).iso / inet / internet-drafts / draft-ietf-frnetmib-fr-04.txt < prev next >

Wrap

Text File | 1993-10-14 | 89.1 KB | 2,951 lines

Internet Draft Frame Relay Service MIB October 14, 1993 Definitions of Managed Objects for Frame Relay Service draft-ieft-frnetmib-fr-04.txt October 14, 1993 Frame Relay Service MIB Working Group Tracy A. Brown (editor) Bell Communications Research 331 Newman Springs Road Red Bank, NJ 07701 tacox@mail.bellcore.com 1. Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress." Please check the I-D abstract listing contained in each Internet Draft directory to learn the current status of this or any other Internet Draft. 2. Abstract This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service. This memo does not specify a standard for the Internet community. T. Brown (editor) Expires 5/14/94 [Page 1] Internet Draft Frame Relay Service MIB October 14, 1993 3. The SNMPv2 Network Management Framework The SNMPv2 Network Management Framework consists of four major components. They are: o RFC 1442 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. o RFC 1213 defines MIB-II, the core set of managed objects for the Internet suite of protocols. o RFC 1445 which defines the administrative and other architectural aspects of the framework. o RFC 1448 which defines the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. T. Brown (editor) Expires 5/14/94 [Page 2] Internet Draft Frame Relay Service MIB October 14, 1993 4. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. T. Brown (editor) Expires 5/14/94 [Page 3] Internet Draft Frame Relay Service MIB October 14, 1993 5. Overview These objects are used when the particular media being used to manage is Frame Relay Service. At present, this applies to these values of the ifType variable in the Internet-standard MIB: frameRelayService (44) This section provides an overview and background of how to use this MIB and other potential MIBs when managing a Frame Relay Service. Figure 1 shows the MIB stack that could be followed for managing a Frame Relay Service. This is only an example and not meant to be inclusive. ____________________________________________________ | | | | | | | | SIP | RFC1490 | | | X.25 MIB | Relay | (no applic.| | | for IW/Encap.| MIB | MIB) | | | | | | | MIB II |-----------------------------------| | | | | ifTable | Frame Relay Service MIB | | ifStackTable |___________________________________| | | | | | | Physical Layer MIBs | ATM MIB | | | e.g., DS1/E1 MIB, |---------| | | RS232-like MIB | Phy. | | | | Layer | | | | MIB | |--------------|-------------------------|---------| Figure 1. Frame Relay MIB Architecture 5.1. Scope of MIB The Frame Relay Service MIB will only manage the Frame Relay portion of the network. This MIB is based upon the Customer Network Management concepts presented in the document "Service Management Architecture for Virtual Connection Services" [6]. T. Brown (editor) Expires 5/14/94 [Page 4] Internet Draft Frame Relay Service MIB October 14, 1993 This MIB will NOT be implemented on User Equipment (e.g., DTE), and the Frame Relay DTE MIB (RFC1315) should be used to manage those devices. Frame Relay Service MIB is intended to be used for Customer Network Management (CNM) of a Frame Relay Network Service. It provides information that allows end-customers to obtain performance monitoring, fault detection, and configuration information about their Frame Relay Service. By using this and other related MIBs, a customer's NMS can monitor their PVCs and UNI/NNI logical ports. Internal aspects of the network (e.g., switching elements, line cards, and network routing tables) are outside the scope of this MIB. The Customer's NMS will typically access the SNMP proxy-agent within the Frame Relay network using SNMP over UDP over IP with IP encapsulated in Frame Relay according to RFC1490/ANSI T1.617 Annex F. The customer, thus, has a PVC to the SNMP proxy-agent. Alternate access mechanisms and SNMP agent implementations are possible. The service capabilities include retrieving information and receiving TRAPs. It is beyond the scope of this MIB to define managed objects to monitor the physical layer. Existing physical layer MIBs (e.g., DS1 MIB) and MIB II will be used as possible. The Frame Relay Service SNMP MIB for CNM will not contain any managed objects to monitor the physical layer. This MIB primarily addresses Frame Relay PVCs. This MIB may be extended at a later time to handle Frame Relay SVCs. This MIB is only used to manage a single Frame Relay Service offering from one network. This MIB will typically be implemented on a service provider's SNMP proxy-agent. The SNMP proxy-agent proxies for all Frame Relay equipment within one service provider's Frame Relay network. (Other SNMP agent implementations are not precluded.) Therefore, this MIB models a PVC segment through one Frame Relay Network. See Figure 2. If the customer's PVCs traverse multiple networks, then the customer needs to poll multiple network proxy-agents within each Frame Relay Network to retrieve their end-to-end view of their service. See Figure 2 and the Service Management Architecture [6]. T. Brown (editor) Expires 5/14/94 [Page 5] Internet Draft Frame Relay Service MIB October 14, 1993 +-------------------------------------+ | Customer Network Management Station | | (SNMP based) | +-------------------------------------+ ^ ^ ^ | | | | | | UNI | NNI | NNI | UNI | ^ | ^ | ^ | +-----------+ | +-----------+ | +-----------+ | | | | | | | | | | | Originating | | FR | | | FR | | | FR | |Terminating +--------+ | | Network I | | | Network J | | | Network K | | +--------+ | | | | | | | | | | | | | | | |----| |---| |---| |----| User B | | | | | | | | | | | | | | | | ////////////////////////////////////////////////////////////// | | | | | | | | | | | | | | | +--------+ | +-----------+ | +-----------+ | +-----------+ | +--------+ | | | | | | | | | PVC Segment 1 | PVC Segment 2 | PVC Segment 3 | |<------------->|<------------->|<------------->| | | | Multi-network PVC | |<--------------------------------------------->| | NNI = Network-to Network Interface | UNI = User-to-Network Interface Figure 2. Multi-network PVC Also, since the Frame Relay network is a shared network amongst many Frame Relay subscribers, each subscriber will only have access to their information (e.g., information with respect to their interfaces and PVCs). Therefore, in order to provide this capability, the Frame Relay PVC CNM proxy agent should be able to support instance level granularity for MIB views. See the Service Management Architecture. T. Brown (editor) Expires 5/14/94 [Page 6] Internet Draft Frame Relay Service MIB October 14, 1993 5.2. Frame Relay Service MIB Terminology Access Channel - An access channel generically refers to the DS1/E1 or DS3/E3-based UNI access channel or NNI access channel across which frame relay data transits. An access channel is the access pathway for a single stream of user data. Within a given T1 line, an access channel can denote any one of the following: o Unchannelized T1 - the entire T1 line is considered an access channel. Each access channel is comprised of 24 T1 time slots. o Channelized T1 - an access channel is any one of 24 channels. Each access channel is comprised of a single T1 time slot. o Fractional T1 - an access channel is a grouping of N T1 time slots (NX56/64 Kbps, where N = 1-23 T1 Time slots per FT1 Access Channel) that may be assigned in consecutive or non-consecutive order. Within a given E1 line, a channel can denote any one of the following: o Unchannelized E1 - the entire E1 line is considered a single access channel. Each access channel is comprised of 31 E1 time slots. o Channelized E1 - an access channel is any one of 31 channels. Each access channel is comprised of a single E1 time slot. o Fractional E1 - an access channel is a grouping of N E1 time slots (NX64 Kbps, where N = 1-30 E1 time slots per FE1 access channel) that may be assigned in consecutive or non-consecutive order. Within a given unformatted line, the entire unformatted line is considered an access channel. Examples include RS-232, V.35, V.36 and X.21 (non- switched). Access Rate - The data rate (expressed in bits/s) of the user access channel. The speed of the access channel determines how much data (maximum rate) the end user can inject into the network. T. Brown (editor) Expires 5/14/94 [Page 7] Internet Draft Frame Relay Service MIB October 14, 1993 Bc - The Committed Burst Size (Bc) is the maximum committed amount of data (expressed in bits) a user may offer to the network during a time interval Tc. Bc is negotiated at call set-up. Be - The Excess Burst Size (Be) is the maximum allowed amount of data (expressed in bits) by which a user can exceed Bc during a time interval Tc. This data (Be) is delivered in general with a lower probability than Bc. Be is negotiated at call set-up. CIR - The Committed Information Rate (CR) is the information transfer rate (expressed in bits/s) at which the network is committed to transfer information under normal conditions. The rate is averaged over a minimum increment of time Tc. CIR is negotiated at call set-up. DLCI - Data Link Connection Identifier Logical Port - This term is used to model the Frame Relay "interface" on a device. NNI - Network to Network Interface Permanent Virtual Connection (PVC) - A virtual connection that has its end-points and bearer capabilities defined at subscription time. Time slot (E1) - An octet within the 256-bit information field in each E1 frame is defined as a time slot. Time slots are position sensitive within the 256-bit information field. Fractional E1 service is provided in contiguous or non- contiguous time slot increments. Time slot (T1) - An octet within the 192-bit information field in each T1 frame is defined as a time slot. Time slots are position sensitive within the 192-bit information field. Fractional T1 service is provided in contiguous or non- contiguous time slot increments. UNI - User to Network Interface N391 - Full status (status of all PVCs) polling counter N392 - Error threshold T. Brown (editor) Expires 5/14/94 [Page 8] Internet Draft Frame Relay Service MIB October 14, 1993 N393 - Monitored events count T391 - Link integrity verification polling timer T392 - Polling verification timer nT3 - Status enquiry timer nN3 - Maximum status enquiry counter 5.3. Apply MIB II to a Frame Relay Service Use the System Group to apply to the SNMP proxy-agent, since the proxy-agent may be monitoring many Frame Relay devices in one network. System Group applies to only one system. This group is not instantiated. sysDescr: ASCII string describing the SNMP proxy-agent. Can be up to 255 characters long. This field is generally used to indicate the network providers identification and type of service offered. sysObjectID: Unique OBJECT IDENTIFIER (OID) for the SNMP proxy-agent. sysUpTime: Clock in the SNMP proxy-agent; TimeTicks in 1/100s of a second. Elapsed type since the proxy-agent came on line. sysContact: Contact for the SNMP proxy-agent. ASCII string of up to 255 characters. sysName: Domain name of the SNMP proxy-agent, for example, acme.com sysLocation: Location of the SNMP proxy-agent. ASCII string of up to 255 characters. sysServices: Services of the managed device. The value "2" which implies that the Frame Relay network is providing a subnetwork level service is recommended. This specifies how the Interfaces Group defined in MIB II shall be used for the management of Frame Relay based T. Brown (editor) Expires 5/14/94 [Page 9] Internet Draft Frame Relay Service MIB October 14, 1993 interfaces, and in conjunction with the Frame Relay Service MIB module. This memo assumes the interpretation of the evolution of the Interfaces group to be in accordance with: "The interfaces table (ifTable) contains information on the managed resource's interfaces. Each sub- layer below the internetwork layer of a network interface is considered an interface." Thus, the ifTable allows the following Frame Relay-based interfaces to be represented as table entries: - Frame Relay interfaces in the Frame Relay equipment (e.g., switches, routers or networks) with Frame Relay interfaces. This level is concerned with generic frame counts and not with individual virtual connections. In accordance with the guidelines of ifTable, frame counts per virtual connection are not covered by ifTable, and are considered interface specific and covered in the Frame Relay Service MIB module. In order to interrelate the ifEntries properly, the Interfaces Stack Group shall be supported. Some specific interpretations of ifTable for Frame Relay follow. Object Use for the generic Frame Relay layer ====== ========================================= ifIndex Each Frame Relay port is represented by an ifEntry. ifDescr Description of the Frame Relay interface. ASCII string describing the UNI/NNI logical port. Can be up to 255 characters long. ifType The value allocated for Frame Relay Service is equal to 44. ifMtu Set to maximum frame size in octets for this frame relay logical port. ifSpeed Peak bandwidth in bits per second available for use. This could be the speed of the logical port and not the access rate. Actual user information transfer rate (i.e., access rate) of the UNI or NNI logical port in bits per second (this is not the clocking T. Brown (editor) Expires 5/14/94 [Page 10] Internet Draft Frame Relay Service MIB October 14, 1993 speed). For example, it is 1,536,000 bits per second for a DS1-based UNI/NNI logical port and 1,984,000 bits per second for an E1-based UNI/NNI logical port. ifPhysAddress The primary address for this logical port assigned by the Frame Relay interface provider. An octet string of zero length if no address is used for this logical port. ifAdminStatus Supports read-only access (initially). The desired administrative status of the frame relay logical port. ifOperStatus The current operational status of the Frame Relay UNI or NNI logical port. ifLastChange The elapsed time since the last re-initialization of the logical port. The value of sysUpTime at the time the logical port entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value. ifInOctets The number of received octets. This counter only counts octets from the beginning of the frame relay header field to the end of user data. ifInUcastPkts The number of received unerrored, unicast frames. ifInDiscards The number of received frames discarded. Possible reasons are as follows: policing, congestion. ifInErrors The number of received frames that are discarded, because of an error. Possible errors can be the following: the frame relay frames were too long or were too short, the frames had an invalid or unrecognized DLCI values, T. Brown (editor) Expires 5/14/94 [Page 11] Internet Draft Frame Relay Service MIB October 14, 1993 or incorrect header values. ifInUnknownProtos noSuchName ifOutOctets The number of transmitted octets. This counter only counts octets from the beginning of the frame relay header field to the end of user data. ifOutUcastpkts The number of frames sent. [Ed. note: Frame Relay switches provide counts of transmitted frames and not of frames received for transmission as required by the ifTable. This is because the latter counter is switch architecture dependent. Comments are requested on this issue.] ifOutDiscards The number of frames discarded in the egress direction. Possible reasons are as follows: policing, congestion. ifOutErrors The number of frames discarded in the egress direction, because of errors. Possible reason is transmit underruns. ifSpecific Set to the OBJECT IDENTIFIER for frLportNumPlan.frLportIfIndex for this ifEntry. ifName noSuchName ifInMulticastPkts The number of received unerrored, multicast frames. ifInBroadcastPkts noSuchName ifOutMulticastPkts The number of sent unerrored, multicast frames. ifOutBroadcastPkts noSuchName ifHCInOctets Only used for DS3-based (and greater) Frame Relay logical ports. The number of received octets. This counter only counts octets from the T. Brown (editor) Expires 5/14/94 [Page 12] Internet Draft Frame Relay Service MIB October 14, 1993 beginning of the frame relay header field to the end of user data. ifHCOutOctets Only used for DS3-based (and greater) Frame Relay logical ports. The number of transmitted octets. This counter only counts octets from the beginning of the frame relay header field to the end of user data. ifLinkUpDownTrapEnble The value of this object is implementation specific for Frame Relay logical ports. ifHighSpeed Set to the user data rate of the frame relay logical port in millions of bits per second. If the user data rate is less than 1 Mbps, then this value is zero. ifPromiscuousMode Set to false(2). Frame Relay Network Service interfaces do not support any other groups or objects in the Interfaces group of MIB II. Also, using the SNMP Group of MIB II is an implementation choice. T. Brown (editor) Expires 5/14/94 [Page 13] Internet Draft Frame Relay Service MIB October 14, 1993 6. Object Definitions FRNETSERV-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Integer32, TimeTicks, experimental FROM SNMPv2-SMI DisplayString, PhysAddress, RowStatus FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; frnetservMIB MODULE-IDENTITY LAST-UPDATED "9310141200Z" ORGANIZATION "IETF Frame Relay Network MIB Working Group" CONTACT-INFO " Tracy A. Brown Bellcore 331 Newman Springs Rd. Red Bank, NJ 07701 USA Tel: 1-908-758-2107 Fax: 1-908-758-4177 E-mail: tacox@mail.bellcore.com." DESCRIPTION "The MIB module to describe generic objects for Frame Relay Network Service." ::= { experimental 45 } frnetservObjects OBJECT IDENTIFIER ::= { frnetservMIB 1 } frnetservTraps OBJECT IDENTIFIER ::= { frnetservMIB 2 } T. Brown (editor) Expires 5/14/94 [Page 14] Internet Draft Frame Relay Service MIB October 14, 1993 -- The Frame Relay Service Logical Port Group -- the Frame Relay Logical Port Group -- This table is an interface specific addendum -- to the generic ifTable from MIB-II. frLportTable OBJECT-TYPE SYNTAX SEQUENCE OF FrLportEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay Logical Port Information table." ::= { frnetservObjects 1 } frLportEntry OBJECT-TYPE SYNTAX FrLportEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay Logical Port Information table." INDEX { frLportIfIndex } ::= { frLportTable 1 } FrLportEntry ::= SEQUENCE { frLportIfIndex Integer32, frLportNumPlan INTEGER, frLportContact DisplayString, frLportLocation DisplayString, frLportType INTEGER, frLportAddrDLCILen INTEGER, frLportVCSigProtocol INTEGER, frLportVCSigPointer OBJECT IDENTIFIER } frLportIfIndex OBJECT-TYPE T. Brown (editor) Expires 5/14/94 [Page 15] Internet Draft Frame Relay Service MIB October 14, 1993 SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to MIB II's ifIndex value for this UNI/NNI logical port." ::= { frLportEntry 1 } frLportNumPlan OBJECT-TYPE SYNTAX INTEGER { other(1), e164(2), x121(3), none(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the network address numbering plan for this UNI/NNI logical port. The network address is the object ifPhysAddress. The value none implies that there is no ifPhysAddress. The SNMP proxy-agent will return an octet string of zero length for ifPhysAddress. The value other means that an address has been assigned to this interface, but the numbering plan is not enumerated here." ::= { frLportEntry 2 } frLportContact OBJECT-TYPE SYNTAX DisplayString (SIZE(0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the network contact for this UNI/NNI logical port." ::= { frLportEntry 3 } frLportLocation OBJECT-TYPE SYNTAX DisplayString (SIZE(0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the Frame Relay network location for this UNI/NNI logical T. Brown (editor) Expires 5/14/94 [Page 16] Internet Draft Frame Relay Service MIB October 14, 1993 port." ::= { frLportEntry 4 } frLportType OBJECT-TYPE SYNTAX INTEGER { uni(1), nni(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the type of network interface for this logical port." ::= { frLportEntry 5 } frLportAddrDLCILen OBJECT-TYPE SYNTAX INTEGER { twoOctets10Bits(1), threeOctets10Bits(2), threeOctets16Bits(3), fourOctets17Bits(4), fourOctets23Bits(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the Q.922 Address field length and DLCI length for this UNI/NNI logical port." ::= { frLportEntry 6 } frLportVCSigProtocol OBJECT-TYPE SYNTAX INTEGER { none(1), lmi(2), ansiT1617D(3), ansiT1617B(4), ccittQ933A(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the Local In-Channel Signaling Protocol that is used for this frame relay UNI/NNI logical port." T. Brown (editor) Expires 5/14/94 [Page 17] Internet Draft Frame Relay Service MIB October 14, 1993 ::= { frLportEntry 7 } frLportVCSigPointer OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is used as a pointer to the table that contains the Local In-Channel Signaling Protocol parameters and errors for this UNI/NNI logical port. See the Frame Relay Management VC Signaling Parameters and Errors Group." ::= { frLportEntry 8 } T. Brown (editor) Expires 5/14/94 [Page 18] Internet Draft Frame Relay Service MIB October 14, 1993 -- the Frame Relay Management VC Signaling Group -- This Group contains managed objects for the -- Local In-Channel Signaling Parameters and -- for signaling errors. frMgtVCSigTable OBJECT-TYPE SYNTAX SEQUENCE OF FrMgtVCSigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay Management VC Signaling Parameters and Errors table." ::= { frnetservObjects 2 } frMgtVCSigEntry OBJECT-TYPE SYNTAX FrMgtVCSigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay Management VC Signaling Parameters Errors table." INDEX { frMgtVCSigIfIndex } ::= { frMgtVCSigTable 1 } FrMgtVCSigEntry ::= SEQUENCE { frMgtVCSigIfIndex Integer32, frMgtVCSigProced INTEGER, frMgtVCSigUserN391 INTEGER, frMgtVCSigUserN392 INTEGER, frMgtVCSigUserN393 INTEGER, frMgtVCSigUserT391 INTEGER, frMgtVCSigNetN392 INTEGER, frMgtVCSigNetN393 INTEGER, frMgtVCSigNetT392 INTEGER, T. Brown (editor) Expires 5/14/94 [Page 19] Internet Draft Frame Relay Service MIB October 14, 1993 frMgtVCSigNetnN4 INTEGER, frMgtVCSigNetnT3 INTEGER, frMgtVCSigUserLinkRelErrors Counter32, frMgtVCSigUserProtErrors Counter32, frMgtVCSigUserChanInactive Counter32, frMgtVCSigNetLinkRelErrors Counter32, frMgtVCSigNetProtErrors Counter32, frMgtVCSigNetChanInactive Counter32 } frMgtVCSigIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to MIB II's ifIndex value for this UNI/NNI logical port." ::= { frMgtVCSigEntry 1 } frMgtVCSigProced OBJECT-TYPE SYNTAX INTEGER { u2nnet(1), bidirect(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the Local In-Channel Signaling Procedure that is used for this UNI/NNI logical port. The UNI/NNI logical port can be performing only user-to-network network-side procedures or bidirectional procedures." ::= { frMgtVCSigEntry 2 } frMgtVCSigUserN391 OBJECT-TYPE SYNTAX INTEGER (1..255) T. Brown (editor) Expires 5/14/94 [Page 20] Internet Draft Frame Relay Service MIB October 14, 1993 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the User-side N391 full status polling cycle value for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this value is equal to noSuchName. This object applies to Q.933 Annex A and T1.617 Annex D." DEFVAL { 6 } ::= { frMgtVCSigEntry 3 } frMgtVCSigUserN392 OBJECT-TYPE SYNTAX INTEGER (1..10) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the User-side N392 error threshold value for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this value is equal to noSuchName. This object applies to Q.933 Annex A and T1.617 Annex D." DEFVAL { 3 } ::= { frMgtVCSigEntry 4 } frMgtVCSigUserN393 OBJECT-TYPE SYNTAX INTEGER (1..10) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the User-side N393 monitored events count value for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this value is equal to noSuchName. This object applies to Q.933 Annex A and T1.617 Annex D." DEFVAL { 4 } ::= { frMgtVCSigEntry 5 } frMgtVCSigUserT391 OBJECT-TYPE SYNTAX INTEGER (5..30) MAX-ACCESS read-only STATUS current DESCRIPTION T. Brown (editor) Expires 5/14/94 [Page 21] Internet Draft Frame Relay Service MIB October 14, 1993 "The value of this object identifies the User-side T391 link integrity verification polling timer value for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this value is equal to noSuchName. This object applies to Q.933 Annex A and T1.617 Annex D." DEFVAL { 10 } ::= { frMgtVCSigEntry 6 } frMgtVCSigNetN392 OBJECT-TYPE SYNTAX INTEGER (1..10) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the Network- side N392 error threshold value (nN2 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this value is equal to noSuchName. This object applies to Q.933 Annex A, T1.617 Annex D and LMI." DEFVAL { 3 } ::= { frMgtVCSigEntry 7 } frMgtVCSigNetN393 OBJECT-TYPE SYNTAX INTEGER (1..10) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the Network- side N393 monitored events count value (nN3 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this value is equal to noSuchName. This object applies to Q.933 Annex A, T1.617 Annex D and LMI." DEFVAL { 4 } ::= { frMgtVCSigEntry 8 } frMgtVCSigNetT392 OBJECT-TYPE SYNTAX INTEGER (5..30) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the Network- T. Brown (editor) Expires 5/14/94 [Page 22] Internet Draft Frame Relay Service MIB October 14, 1993 side T392 polling verification timer value (nT2 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this value is equal to noSuchName. This object applies to Q.933 Annex A, T1.617 Annex D and LMI." DEFVAL { 15 } ::= { frMgtVCSigEntry 9 } frMgtVCSigNetnN4 OBJECT-TYPE SYNTAX INTEGER (5..5) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the Network- side nN4 maximum status enquires received value for this UNI/NNI logical port. If the logical port is not performing network-side procedures or is not performing LMI procedures, then this value is equal to noSuchName. This object applies only to LMI and always has a value of 5." ::= { frMgtVCSigEntry 10 } frMgtVCSigNetnT3 OBJECT-TYPE SYNTAX INTEGER (5 | 10 | 15 | 20 | 25 | 30) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the Network- side nT3 timer (for nN4 status enquires received) value for this UNI/NNI logical port. If the logical port is not performing network-side procedures or is not performing LMI procedures, then this value is equal to noSuchName. This object applies only to LMI." DEFVAL { 20 } ::= { frMgtVCSigEntry 11 } frMgtVCSigUserLinkRelErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of user-side local in-channel signaling link reliability errors (i.e., non- T. Brown (editor) Expires 5/14/94 [Page 23] Internet Draft Frame Relay Service MIB October 14, 1993 receipt of Status/Status Enquiry messages or invalid sequence numbers in a Link Integrity Verification Information Element) for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this value is equal to noSuchName." ::= { frMgtVCSigEntry 12 } frMgtVCSigUserProtErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of user-side local in-channel signaling protocol errors (i.e., protocol discriminator, message type, call reference, and mandatory information element errors) for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this value is equal to noSuchName." ::= { frMgtVCSigEntry 13 } frMgtVCSigUserChanInactive OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times the user-side channel was declared inactive (i.e., N392 errors in N393 events) for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this value is equal to noSuchName." ::= { frMgtVCSigEntry 14 } frMgtVCSigNetLinkRelErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of network-side local in-channel signaling link reliability errors (i.e., non- receipt of Status/Status Enquiry messages or invalid sequence numbers in a Link Integrity Verification Information Element) for this UNI/NNI T. Brown (editor) Expires 5/14/94 [Page 24] Internet Draft Frame Relay Service MIB October 14, 1993 logical port. If the logical port is not performing network-side procedures, then this value is equal to noSuchName." ::= { frMgtVCSigEntry 15 } frMgtVCSigNetProtErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of network-side local in-channel signaling protocol errors (i.e., protocol discriminator, message type, call reference, and mandatory information element errors) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this value is equal to noSuchName." ::= { frMgtVCSigEntry 16 } frMgtVCSigNetChanInactive OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times the network-side channel was declared inactive (i.e., N392 errors in N393 events) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this value is equal to noSuchName." ::= { frMgtVCSigEntry 17 } T. Brown (editor) Expires 5/14/94 [Page 25] Internet Draft Frame Relay Service MIB October 14, 1993 -- The Frame Relay PVC Connection Group -- The Frame Relay PVC Connection Group -- models a bi-directional PVC flow -- as two uni-directional -- PVC flows. -- Frame Relay Network Frame Relay Network -- Ingress ____________________________________ Egress -- | | -- ______| >> uni-directional PVC flow >> |____________ -- |___________________________________| -- -- Frame Relay Network Frame Relay Network -- Egress ____________________________________ Ingress -- | | -- ______| << uni-directional PVC flow << |____________ -- |___________________________________| -- -- The two uni-directional PVC flows provide information -- in the ingress to egress direction. -- Ingress is defined as going into the Frame Relay Network, -- and egress is defined as going out of the Frame -- Relay Network. -- If the Frame Relay Connection table is used to model -- a unidirectional PVC, then there is only one entry in this -- table for this unidirectional PVC. Performing a GET-Request by -- indexing the table in the reverse direction -- will return a noSuchName. -- A PVC segment flow is a portion of a PVC -- that traverses one Frame Relay Network, and -- a PVC segment flow is identified -- by its two end-points (UNI/NNI logical port index -- value and DLCI index value) -- through one Frame Relay Network. frPVCConnectTable OBJECT-TYPE SYNTAX SEQUENCE OF FrPVCConnectEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay PVC Connect table. A bi- directional PVC flow is modeled as two entries in T. Brown (editor) Expires 5/14/94 [Page 26] Internet Draft Frame Relay Service MIB October 14, 1993 this table. Each entry models a uni-directional PVC flow." ::= { frnetservObjects 3 } frPVCConnectEntry OBJECT-TYPE SYNTAX FrPVCConnectEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay PVC Connect table. This entry is used to model a PVC segment flow in one direction." INDEX { frPVCConnectIngressIfIndex, frPVCConnectIngressDLCIIndex, frPVCConnectEgressIfIndex, frPVCConnectEgressDLCIIndex } ::= { frPVCConnectTable 1 } FrPVCConnectEntry ::= SEQUENCE { frPVCConnectIngressIfIndex Integer32, frPVCConnectIngressDLCIIndex Integer32, frPVCConnectEgressIfIndex Integer32, frPVCConnectEgressDLCIIndex Integer32, frPVCConnectAdminStatus INTEGER, frPVCConnectOperStatus INTEGER, frPVCConnectLastChange TimeTicks, frPVCConnectMaxFrameSize Integer32, frPVCConnectBc Integer32, frPVCConnectBe Integer32, frPVCConnectCIR Integer32, frPVCConnectGenericPointer OBJECT IDENTIFIER, frPVCConnectStatus RowStatus } T. Brown (editor) Expires 5/14/94 [Page 27] Internet Draft Frame Relay Service MIB October 14, 1993 frPVCConnectIngressIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to MIB II's ifIndex value for the ingress UNI/NNI logical port for this uni-directional PVC flow." ::= { frPVCConnectEntry 1 } frPVCConnectIngressDLCIIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to the ingress DLCI value for this uni-directional PVC flow." ::= { frPVCConnectEntry 2 } frPVCConnectEgressIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to MIB II's ifIndex value for the egress UNI/NNI logical port for this uni-directional PVC flow. If the value is equal to zero, then the egress logical port is not a frame relay UNI/NNI logical port." ::= { frPVCConnectEntry 3 } frPVCConnectEgressDLCIIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to the egress DLCI value for this uni-directional PVC flow. If the value is equal to zero, then the egress end of the PVC flow is not a Frame Relay connection." ::= { frPVCConnectEntry 4 } frPVCConnectAdminStatus OBJECT-TYPE SYNTAX INTEGER { deleted(1), T. Brown (editor) Expires 5/14/94 [Page 28] Internet Draft Frame Relay Service MIB October 14, 1993 active(2), inactive(3), testing(4) } MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the desired administrative status of this uni-directional PVC flow. This state is set by an administrative entity. This value affects the PVC status indicated across the ingress NNI/UNI of the uni- directional PVC flow." ::= { frPVCConnectEntry 5 } frPVCConnectOperStatus OBJECT-TYPE SYNTAX INTEGER { deleted(1), active(2), inactive(3), testing(4), unknown(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the current operational status of this uni-directional PVC flow. This value affects the PVC status indicated across the ingress NNI/UNI of the uni-directional PVC flow." ::= { frPVCConnectEntry 6 } frPVCConnectLastChange OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time this uni- directional PVC flow entered its current operational state. If the current state was entered prior to the last re-initialization of the proxy-agent, then this object contains a zero value." ::= { frPVCConnectEntry 7 } T. Brown (editor) Expires 5/14/94 [Page 29] Internet Draft Frame Relay Service MIB October 14, 1993 frPVCConnectMaxFrameSize OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is the size in octets of the largest frame relay information field for this uni-directional PVC flow in the ingress direction (into the frame relay network). The value of frPVCConnectMaxFrameSize must be less than or equal to the corresponding ifMtu for this Frame Relay UNI/NNI logical port." ::= { frPVCConnectEntry 8 } frPVCConnectBc OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is equal to the committed burst size (Bc) parameter (measured in bits) for this uni-directional PVC flow." ::= { frPVCConnectEntry 9 } frPVCConnectBe OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is equal to the excess burst size (Be) parameter (measured in bits) for this uni-directional PVC flow." ::= { frPVCConnectEntry 10 } frPVCConnectCIR OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is equal to the committed information rate (CIR) parameter (measured in bits per second) for this uni- directional PVC flow." ::= { frPVCConnectEntry 11 } T. Brown (editor) Expires 5/14/94 [Page 30] Internet Draft Frame Relay Service MIB October 14, 1993 frPVCConnectGenericPointer OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object is used as a pointer to the Generic VC Table. This OID should contain the appropriate ifIndex and vcIndex values for the Generic VC Table." ::= { frPVCConnectEntry 12 } frPVCConnectStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this entry in the frPVCConnectTable. This variable is used to create new PVC segment flows and to change existing PVC segment flows. This capability may not be supported for all implementations." ::= { frPVCConnectEntry 13 } T. Brown (editor) Expires 5/14/94 [Page 31] Internet Draft Frame Relay Service MIB October 14, 1993 -- The PVC End-Point Group -- This table provides statistics for a PVC segment -- End-point. -- A PVC segment end-point is identified by a UNI/NNI -- logical port index value and DLCI index value. frPVCEndptTable OBJECT-TYPE SYNTAX SEQUENCE OF FrPVCEndptEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay PVC End-Point table. This Table is used to model a PVC end-point. This table contains the statistics for a PVC end-point." ::= { frnetservObjects 4 } frPVCEndptEntry OBJECT-TYPE SYNTAX FrPVCEndptEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay PVC Endpt table." INDEX { frPVCEndptIfIndex, frPVCEndptDLCIIndex } ::= { frPVCEndptTable 1 } FrPVCEndptEntry ::= SEQUENCE { frPVCEndptIfIndex Integer32, frPVCEndptDLCIIndex Integer32, frPVCEndptRcvdSigStatus INTEGER, frPVCEndptInFrames Counter32, frPVCEndptOutFrames Counter32, frPVCEndptInDEFrames Counter32, frPVCEndptInExcessFrames Counter32, frPVCEndptOutExcessFrames T. Brown (editor) Expires 5/14/94 [Page 32] Internet Draft Frame Relay Service MIB October 14, 1993 Counter32, frPVCEndptInDiscards Counter32, frPVCEndptInOctets Counter32, frPVCEndptOutOctets Counter32 } frPVCEndptIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to MIB II's ifIndex value for this UNI/NNI logical port." ::= { frPVCEndptEntry 1 } frPVCEndptDLCIIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to the DLCI value for this PVC segment end-point." ::= { frPVCEndptEntry 2 } frPVCEndptRcvdSigStatus OBJECT-TYPE SYNTAX INTEGER { deleted(1), active(2), inactive(3), none(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the PVC status received via the local in-channel signaling procedures for this PVC segment end-point. This object is only pertinent for interfaces that perform the bidirectional procedures. For user- to-network network side procedures, the value of this object should be none." ::= { frPVCEndptEntry 3 } T. Brown (editor) Expires 5/14/94 [Page 33] Internet Draft Frame Relay Service MIB October 14, 1993 frPVCEndptInFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames received by the network (ingress) for this PVC segment end-point. This includes any frames discarded by the network due to submitting more than Bc + Be data or due to any network congestion recovery procedures." ::= { frPVCEndptEntry 4 } frPVCEndptOutFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames sent by the network (egress) regardless of whether they are Bc or Be frames for this PVC segment end-point." ::= { frPVCEndptEntry 5 } frPVCEndptInDEFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames received by the network (ingress) with the DE bit set to (1) for this PVC segment end-point." ::= { frPVCEndptEntry 6 } frPVCEndptInExcessFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames received by the network (ingress) for this PVC segment end-point which were treated as excess traffic. Frames which are sent to the network with DE set to zero are treated as excess when more than Bc bits are submitted to the network during the Committed Information Rate Measurement Interval (Tc). Excess traffic may or may not be discarded at the T. Brown (editor) Expires 5/14/94 [Page 34] Internet Draft Frame Relay Service MIB October 14, 1993 ingress if more than Bc + Be bits are submitted to the network during Tc. Traffic discarded at the ingress is not recorded in frPVCEndptInExcessFrames. Frames which are sent to the network with DE set to one are also treated as excess traffic." ::= { frPVCEndptEntry 7 } frPVCEndptOutExcessFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames sent by the network (egress) for this PVC segment end-point which were treated as excess traffic. (The DE bit may be set to one.)" ::= { frPVCEndptEntry 8 } frPVCEndptInDiscards OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of frames received by the the network (ingress) that were discarded due to traffic enforcement for this PVC segment end-point." ::= { frPVCEndptEntry 9 } frPVCEndptInOctets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets received by the network (ingress) for this PVC segment end-point. This counter should only count octets from the beginning of the frame relay header field to the end of user data. If the network supporting Frame Relay can not count octets, then this count should be an approximation." ::= { frPVCEndptEntry 10 } frPVCEndptOutOctets OBJECT-TYPE SYNTAX Counter32 T. Brown (editor) Expires 5/14/94 [Page 35] Internet Draft Frame Relay Service MIB October 14, 1993 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets sent by the network (egress) for this PVC segment end-point. This counter should only count octets from the beginning of the frame relay header field to the end of user data. If the network supporting Frame Relay can not count octets, then this count should be an approximation." ::= { frPVCEndptEntry 11 } T. Brown (editor) Expires 5/14/94 [Page 36] Internet Draft Frame Relay Service MIB October 14, 1993 -- The Frame Relay Accounting Groups -- The groups are the following: -- Accounting on a PVC basis -- Accounting on an Interface/Logical Port basis -- The Accounting on a Frame Relay PVC basis Group -- The accounting information is collected for a PVC -- segment end-point. frAccountPVCTable OBJECT-TYPE SYNTAX SEQUENCE OF FrAccountPVCEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay Accounting PVC table. This Table is used to perform accounting on a PVC segment end-point basis." ::= { frnetservObjects 5 } frAccountPVCEntry OBJECT-TYPE SYNTAX FrAccountPVCEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay Accounting PVC table." INDEX { frAccountPVCIfIndex, frAccountPVCDLCIIndex } ::= { frAccountPVCTable 1 } FrAccountPVCEntry ::= SEQUENCE { frAccountPVCIfIndex Integer32, frAccountPVCDLCIIndex Integer32, frAccountPVCSegmentSize Integer32, frAccountPVCInSegments Counter32, frAccountPVCOutSegments Counter32 } T. Brown (editor) Expires 5/14/94 [Page 37] Internet Draft Frame Relay Service MIB October 14, 1993 frAccountPVCIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to MIB II's ifIndex value for this UNI/NNI logical port." ::= { frAccountPVCEntry 1 } frAccountPVCDLCIIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to the DLCI value for this PVC segment end-point." ::= { frAccountPVCEntry 2 } frAccountPVCSegmentSize OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is equal to the Segment Size for this PVC segment end-point." ::= { frAccountPVCEntry 3 } frAccountPVCInSegments OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is equal to the number of segments received by this PVC segment end- point." ::= { frAccountPVCEntry 4 } frAccountPVCOutSegments OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is equal to the number of segments sent by this PVC segment end-point." ::= { frAccountPVCEntry 5 } T. Brown (editor) Expires 5/14/94 [Page 38] Internet Draft Frame Relay Service MIB October 14, 1993 -- The Accounting on a Frame Relay Logical Port basis Group frAccountLportTable OBJECT-TYPE SYNTAX SEQUENCE OF FrAccountLportEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Frame Relay Accounting Logical Port table. This Table is used to perform accounting on a UNI/NNI Logical Port basis." ::= { frnetservObjects 6 } frAccountLportEntry OBJECT-TYPE SYNTAX FrAccountLportEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Frame Relay Accounting Logical Port table." INDEX { frAccountLportIfIndex } ::= { frAccountLportTable 1 } FrAccountLportEntry ::= SEQUENCE { frAccountLportIfIndex Integer32, frAccountLportSegmentSize Integer32, frAccountLportInSegments Counter32, frAccountLportOutSegments Counter32 } frAccountLportIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is equal to MIB II's ifIndex value for this UNI/NNI logical port." ::= { frAccountLportEntry 1 } frAccountLportSegmentSize OBJECT-TYPE T. Brown (editor) Expires 5/14/94 [Page 39] Internet Draft Frame Relay Service MIB October 14, 1993 SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is equal to the Segment Size for this UNI/NNI logical port." ::= { frAccountLportEntry 2 } frAccountLportInSegments OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is equal to the number of segments received by this UNI/NNI logical port." ::= { frAccountLportEntry 3 } frAccountLportOutSegments OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is equal to the number of segments sent by this UNI/NNI logical port." ::= { frAccountLportEntry 4 } T. Brown (editor) Expires 5/14/94 [Page 40] Internet Draft Frame Relay Service MIB October 14, 1993 -- Frame Relay Network Service TRAPS frPVCConnectStatusChange NOTIFICATION-TYPE OBJECTS { frPVCConnectIngressIfIndex, frPVCConnectIngressDLCIIndex, frPVCConnectEgressIfIndex, frPVCConnectEgressDLCIIndex, frPVCConnectOperStatus, frPVCEndptRcvdSigStatus } STATUS current DESCRIPTION "This trap indicates that the indicated PVC has changed state. This trap is not sent if an FR-UNI changes state; a linkDown or linkUp trap should be sent instead." ::= { frnetservTraps 1 } T. Brown (editor) Expires 5/14/94 [Page 41] Internet Draft Frame Relay Service MIB October 14, 1993 -- Conformance Information frnetservConformance OBJECT IDENTIFIER ::= { frnetservMIB 3 } frnetservGroups OBJECT IDENTIFIER ::= { frnetservConformance 1 } frnetservCompliances OBJECT IDENTIFIER ::= { frnetservConformance 2 } -- Compliance Statements frnetservCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMPv2 entities which have Frame Relay Network Service Interfaces." MODULE -- this module MANDATORY-GROUPS { frnetservLportGroup, frnetservMgtVCSigGroup, frnetservPVCConnectGroup, frnetservPVCEndptGroup } GROUP frnetservAccountPVCGroup DESCRIPTION "This group is optional for Frame Relay interfaces. It is mandatory if and only if accounting is performed on a PVC basis this Frame Relay interface." GROUP frnetservAccountLportGroup DESCRIPTION "This group is optional for Frame Relay interfaces. It is mandatory if and only if accounting is performed on a logical port basis this Frame Relay interface." OBJECT frPVCConnectAdminStatus SYNTAX INTEGER { deleted(1), active(2), inactive(3), testing(4) T. Brown (editor) Expires 5/14/94 [Page 42] Internet Draft Frame Relay Service MIB October 14, 1993 } MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frPVCConnectMaxFrameSize SYNTAX Integer32 MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frPVCConnectBc SYNTAX Integer32 MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frPVCConnectBe SYNTAX Integer32 MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frPVCConnectCIR SYNTAX Integer32 MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frPVCConnectGenericPointer SYNTAX OBJECT IDENTIFIER MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frPVCConnectStatus SYNTAX INTEGER { active(1) } -- subset of RowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required, and only one of the six enumerated values for the RowStatus textual convention need be supported, specifically: active(1)." ::= { frnetservCompliances 1 } T. Brown (editor) Expires 5/14/94 [Page 43] Internet Draft Frame Relay Service MIB October 14, 1993 -- Units of Conformance frnetservLportGroup OBJECT-GROUP OBJECTS { frLportNumPlan, frLportContact, frLportLocation, frLportType, frLportAddrDLCILen, frLportVCSigProtocol, frLportVCSigPointer } STATUS current DESCRIPTION "A collection of objects providing information applicable to a Frame Relay Logical Port." ::= { frnetservGroups 1 } frnetservMgtVCSigGroup OBJECT-GROUP OBJECTS { frMgtVCSigProced, frMgtVCSigUserN391, frMgtVCSigUserN392, frMgtVCSigUserN393, frMgtVCSigUserT391, frMgtVCSigNetN392, frMgtVCSigNetN393, frMgtVCSigNetT392, frMgtVCSigNetnN4, frMgtVCSigNetnT3, frMgtVCSigUserLinkRelErrors, frMgtVCSigUserProtErrors, frMgtVCSigUserChanInactive, frMgtVCSigNetLinkRelErrors, frMgtVCSigNetProtErrors, frMgtVCSigNetChanInactive } STATUS current DESCRIPTION "A collection of objects providing information applicable to the Local In-Channel Signaling Procedures used for a UNI/NNI logical port." ::= { frnetservGroups 2 } frnetservPVCConnectGroup OBJECT-GROUP OBJECTS { frPVCConnectAdminStatus, frPVCConnectOperStatus, frPVCConnectLastChange, frPVCConnectMaxFrameSize, frPVCConnectBc, frPVCConnectBe, frPVCConnectCIR, frPVCConnectGenericPointer, frPVCConnectStatus } T. Brown (editor) Expires 5/14/94 [Page 44] Internet Draft Frame Relay Service MIB October 14, 1993 STATUS current DESCRIPTION "A collection of objects providing information applicable to a Frame Relay PVC connection." ::= { frnetservGroups 3 } frnetservPVCEndptGroup OBJECT-GROUP OBJECTS { frPVCEndptRcvdSigStatus, frPVCEndptInFrames, frPVCEndptOutFrames, frPVCEndptInDEFrames, frPVCEndptInExcessFrames, frPVCEndptOutExcessFrames, frPVCEndptInDiscards, frPVCEndptInOctets, frPVCEndptOutOctets } STATUS current DESCRIPTION "A collection of objects providing information application to a Frame Relay PVC end-point." ::= { frnetservGroups 4 } frnetservAccountPVCGroup OBJECT-GROUP OBJECTS { frAccountPVCSegmentSize, frAccountPVCInSegments, frAccountPVCOutSegments } STATUS current DESCRIPTION "A collection of objects providing accounting information application to a Frame Relay PVC end-point." ::= { frnetservGroups 5 } frnetservAccountLportGroup OBJECT-GROUP OBJECTS { frAccountLportSegmentSize, frAccountLportInSegments, frAccountLportOutSegments } STATUS current DESCRIPTION "A collection of objects providing accounting information application to a Frame Relay logical port." ::= { frnetservGroups 6 } END T. Brown (editor) Expires 5/14/94 [Page 45] Internet Draft Frame Relay Service MIB October 14, 1993 9. Acknowledgments This document was produced jointly by the Frame Relay Forum Technical Committee MIB Working Group and the Frame Relay Service MIB Working Group. T. Brown (editor) Expires 5/14/94 [Page 46] Internet Draft Frame Relay Service MIB October 14, 1993 10. References [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1442, SNMP Research, Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993. [2] Galvin, J., and K. McCloghrie, "Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1445, Trusted Information Systems, Hughes LAN Systems, April 1993. [3] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1448, SNMP Research, Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993. [4] McCloghrie, K., and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets - MIB-II", RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991. [5] K. McCloghrie and F. Kastenholz, Evolution of Interfaces Group of MIB-II, Internet Draft, September 20, 1993. [6] K. R. Rodemann, Service Management Architecture for Virtual Connection Services, Internet-Draft, July 1993. [7] ANSI T1.617-1991, American National Standard for Telecommunications - Integrated Services Digital Network (ISDN) - Digital Subscriber Signaling System No. 1 (DSS1) - Signaling Specification for Frame Relay Bearer Service. [8] Management Information Base for Frame Relay DTEs, RFC 1315, C. Brown, F. Baker, and C. Carvalho (editors), Internet Engineering Task Force, Network Information Center, SRI International, Menlo Park, CA, April 1992. [9] Multi-Protocol Interconnect over Frame Relay, RFC 1490, T. Brown (editor) Expires 5/14/94 [Page 47] Internet Draft Frame Relay Service MIB October 14, 1993 Obsoletes RFC 1294, T. Bradley, C. Brown, A. Malis, Network Information Center, SRI International, Menlo Park, CA, July 1993. T. Brown (editor) Expires 5/14/94 [Page 48] Internet Draft Frame Relay Service MIB October 14, 1993 11. Security Considerations Security issues are not discussed in this memo. 12. Authors' Addresses Tracy A. Brown Bell Communications Research 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020 Phone: (908) 758-2107 EMail: tacox@mail.bellcore.com T. Brown (editor) Expires 5/14/94 [Page 49] Internet Draft Frame Relay Service MIB October 14, 1993 Table of Contents 1 Status of this Memo ................................... 1 2 Abstract .............................................. 1 3 The SNMPv2 Network Management Framework ............... 2 4 Object Definitions .................................... 3 5 Overview .............................................. 4 5.1 Scope of MIB ........................................ 4 5.2 Frame Relay Service MIB Terminology ................. 7 5.3 Apply MIB II to a Frame Relay Service ............... 9 6 Object Definitions .................................... 14 6.1 The Frame Relay Service Logical Port Group .......... 15 6.2 The Frame Relay Management VC Signaling Group ....... 19 6.3 Frame Relay PVC Connection Group .................... 26 6.4 The PVC End-Point Group ............................. 32 6.5 Frame Relay Accounting Groups ....................... 37 7 Frame Relay Network Service TRAPS ..................... 41 8 Conformance Information ............................... 42 9 Acknowledgments ....................................... 46 10 References ........................................... 47 11 Security Considerations .............................. 49 12 Authors' Addresses ................................... 49 T. Brown (editor) Expires 5/14/94 [Page 50]